Curse

Norris Is King · Oct 15, 2010, 06:30 PM // 18:30

Hello. Recently, I've been afflicted with game crashes followed by Data Archive Repair. Whenever I let the computer run the data archive (I usually switch inputs and play Xbox) my computer reboots itself automatically, and the repair fails. This has never happened to me before until 4 days ago. Since 4 days ago, I've had to re-install twice now. Doing the -image trick takes ages, and I really don't want to have to sit through it again. What is causing my game to crash and causing the data to corrupt? I totally deleted my guildwars folder, with my templates and everything. If you need any additional information to assist me, please don't hesitate to ask. I'll be refreshing every 15-30 minutes or so. Thank you for your help in advance.

Snograt · Oct 15, 2010, 07:09 PM // 19:09

Wish I knew - mine goes through phases of "repairing data archive" - does it for a day or two, then goes back to normal for a few months.

More importantly, what is causing your computer to crash? It crashes while running GW, then it crashes while running repair. Hmm.

Need more symptoms - but I know you're running XP because you said your templates were in the GW folder

Norris Is King · Oct 15, 2010, 08:06 PM // 20:06

Today, I was running GW, running myself from some outpost in Tyria, and it appeared as if the non explorabled parts of the map were covered in black, as if i was using texmod, then GW froze when i tried to move the map with right click, tried to window out, and that was all she wrote.

Elder III · Oct 15, 2010, 10:47 PM // 22:47

sounds like a corrupted gw.dat file --- just run -image overnight, it shouldn't take more than 6 hours on dsl.

Chrisworld · Oct 16, 2010, 12:22 AM // 00:22

Yup. Just get yourself a new DAT file as stated above. When one gets damaged, they can try to repair it, but sometimes it's usually better to start fresh. Texture addresses get lost or damaged .. etc ..

Snograt · Oct 16, 2010, 02:19 PM // 14:19

So delete gw.dat then run -image

Quaker · Oct 16, 2010, 02:58 PM // 14:58

There is also a small possibility that the problem could be caused by bad sectors on the hard drive or bad RAM.

It would have to be very coincidental for gw.dat to happen to be in an area with a bad sector, but it is large, and therefore covers quite a number of sectors. A scan for bad sectors could take a long time, but another way to check would be to copy gw.dat to some other folder, rename the original to something else like gw.bak, then move the copy of gw.dat back to the original folder. That would probably move gw.dat out of any bad sectors.

For bad RAM, you would probably have the computer giving you other errors, such as Registry errors, if that was the problem.